Fixed #73

Hi @vic-w and @d-kleine, could you tell me if everything works on your end?

I am a Windows user, therefore unfortunately I cannot test the IsaacLab features powered by uv, see isaac-sim/IsaacLab#3438

Great work so far – I only have some smaller observations regarding the uv changes:

• License missing in pyproject.yaml
• Description blank in pyproject.yaml
• "Clone the repository." section has wrong information in README

I'm not using what they do, it's independant and I actually wanted to test it on Windows to see if it could work, so let's see with your machine if it could work!

And good catch, I'll update!

There is still path issue here:

import isaac_so_arm101.tasks  # noqa: F401
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'isaac_so_arm101'

Affects multiple files due to the refactoring

what were you running?

Nevermind, I didn't see that you also restructured the repo.

Just tested, up to uv run list_envs it worked so far. Running uv run train --task SO-ARM100-Reach-v0 --headless isn't possible due to the windows/uv issue, but with train --task SO-ARM100-Reach-v0 --headless this error was returned:

gymnasium.error.NameNotFound: Environment `SO-ARM100-Reach` doesn't exist. Did you mean: `Isaac-SO-ARM100-Reach`?

This is needs to be fixed in the README (dummy agents and reaching tasks):
https://github.com/MuammerBay/isaac_so_arm101?tab=readme-ov-file#reaching

My app crashes when running the correct task. I think this is due to dependency conflicts. I have checked that with uv pip check:

Checked 187 packages in 58ms
Found 4 incompatibilities
The package `isaacsim-core` requires `filelock==3.13.1`, but `3.15.4` is installed
The package `isaacsim-core` requires `fsspec==2024.6.1`, but `2024.10.0` is installed
The package `isaacsim-core` requires `networkx==3.3`, but `3.4.2` is installed
The package `isaacsim-core` requires `pywin32==306`, but `311` is installed

I have used my primary IsaacLab (pre-built binary installation), this works for uv run train --task Isaac-SO-ARM100-Reach-v0

True, I forgot to update the task ID!

I'll try to check tonight on a windows installation of my own then, it is weird that uv run list_envs work but not uv run train --task My-Task-Id

Could you try to clone the repository in a completely different location with no virtual environment activated etc and run

uv run zero_agent --task Isaac-SO-ARM100-Reach-v0 --headless --num_envs 1

it is weird that uv run list_envs work but not uv run train --task My-Task-Id

uv run list_envs outputs the env table correct, but also returns some error messages:

TypeError: post_quit(): incompatible function arguments. The following argument types are supported:
    1. (self: omni.kit.app._app.IApp, return_code: int = 0) -> None

This also supports my assumption that the venv is broken (your pyproject.toml setup looks fine though)

Is there a reason why you have used this unsafe strategy?

for convenience as i have multiple packages index configured!

Okay 👌🏻

So, regarding the uv changes, everything's fine from my point-of-view. Only the tasks need to be updated in the README.

I said it in another issue but if you want to do the PR for the task ID naming, I'd be glad to accept it!